Curse

weemanpow3 · Jul 22, 2008, 06:20 PM // 18:20

every so offten (3-5 times day) I get disconnected, Then I try to press retry and I get 007 error. The way I found to get around it is hardboot when retry screen comes up. I have also been getting freezes when guild wars locks up and I have to hardboot. This all started happening when the dragon festival started. Lots of my guild members have the same problem to. I contacted aNet and they just tell me its my isp problem and im getting packet loss, but all my other fully online games work perfect.

toastgodsupreme · Jul 22, 2008, 06:32 PM // 18:32

Let's not troubleshoot or anything before bugging the folks at ANET. /sarcasm

What have you tried so far?

Have you tried deleting/renaming your dat file and see if that changes anything?

Have you bothered to change any settings on your system at all?

Have you done any traceroutes to the servers to see how your connection looks?

I left my tech support psychic hat at the airport so I need to actually ask you these things.

Xx Da Best Xx · Jul 22, 2008, 06:36 PM // 18:36

I've been having the same problem...Usually i just reset my router and it does fine till the next day.

Kattar · Jul 22, 2008, 06:42 PM // 18:42

Are you running ZoneAlarm and Windows?

Quote:

Originally Posted by Painbringer

Microsofts Letter addressing the recent update and conflicts it caused http://blogs.technet.com/msrc/archiv...-ms08-037.aspx

Revision for MS08-037
Hello,

This is Christopher Budd. I wanted to take a moment and let you know about a revision that we’ve made to MS08-037 today.

After the release of MS08-037, we became aware of reports of ZoneAlarm customers experiencing issues after applying the security updates. We started investigating these reports as soon as we heard about them and have been working to research this issue. We’re still working on this issue but we do have some information from our investigation so far, which we’ve put into the bulletin.

Specifically, we’ve identified that customers who are running either ZoneAlarm or Check Point Endpoint Security (previously named Check Point Integrity) who apply MS08-037 may lose network connectivity after applying these updates. Our investigation so far has shown that no other customers are affected by this issue.

We’re still investigating this issue but we encourage customers who are using ZoneAlarm to review the appropriate ZoneAlarm Web site and Check Point Endpoint customers to review the appropriate Check Point Web site for the latest guidance or software updates and factor this information into your risk assessment, testing, and deployment planning.

We will update the bulletin and the MSRC weblog with more information as we have it.

Thanks.

Christopher

weemanpow3 · Jul 22, 2008, 11:36 PM // 23:36

here is the details

MacBook Pro 2.5GHz Penryn
Video Drivers - 177.41
Latest drivers everything else including DirectX, sound

I have Boot Camp and its running Windows Vista Ultimate x64 SP1.
No antivirus or any of thoes programs on. (I only use for games nothing else)
I went and reset modem and router to factory default settings.

Still no luck

RiceCream · Jul 23, 2008, 02:50 AM // 02:50

downgrade to XP Pro SP2.

i've recently been having issues with GW on my macpro w/ bootcamp. GW dies but vent doesnt. hadnt been having issues until i ran updates about a week ago (i dont update often)

toastgodsupreme · Jul 23, 2008, 10:14 PM // 22:14

Quote:

Originally Posted by weemanpow3

here is the details

MacBook Pro 2.5GHz Penryn
Video Drivers - 177.41
Latest drivers everything else including DirectX, sound

I have Boot Camp and its running Windows Vista Ultimate x64 SP1.
No antivirus or any of thoes programs on. (I only use for games nothing else)
I went and reset modem and router to factory default settings.

Still no luck

So again... either you haven't tried anything or you're leaving things out.

I'm not even going to bother trying to help you if you don't help me help you.

An idea of what you could've tried, on your own, had common sense been present...

Quote:

Attempted solutions:

1. -repair
2. -image (after renaming your dat file)
3. Used Contig on the dat file
6. Disabled all unneeded services and programs (through services.msc and the Startup control panel applet)
7. Changed video settings to low

also...

-nosound
-noshaders

Not to mention the fact that you make no effort to tell us what, if any, settings within Windows have been changed. Nor have you told us if you've tried to adjust your D3D settings on your video card. ETC ETC ETC